-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always creates SymbolToField "id"
instance
#1497
Always creates SymbolToField "id"
instance
#1497
Conversation
c02adcb
to
beb58c2
Compare
beb58c2
to
17cbadb
Compare
- given there is always a {EntityName}Id type
4b90e8d
to
04728c2
Compare
SymbolToField "id"
instance
persistent/ChangeLog.md
Outdated
## Unreleased | ||
|
||
* [1497](https://github.com/yesodweb/persistent/pull/1497) | ||
* Always generates `SymbolToField "id"` instance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need to be a minor version bump - may be best to roll up with #1503
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds reasonable to me. Anything I need to do / pay attention to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I've finished everything that needed to be done in #1503 (re-requested review to be sure). Aside from this PR, is anything else planned for 2.14.6.0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll rebase after #1503 has been merged (adjust the changelog section)
This builds and tests just fine locally so I am going to merge. Thank you! |
Context
{EntityName}Id
type hence I think it's safe to always create aSymbolToField
instance for ID.